
<!DOCTYPE html>
<!--

    Copyright (c) 2017, 2019 Oracle and/or its affiliates. All rights reserved.

    This program and the accompanying materials are made available under the
    terms of the Eclipse Public License v. 2.0, which is available at
    http://www.eclipse.org/legal/epl-2.0.

    This Source Code may also be made available under the following Secondary
    Licenses when the conditions for such availability set forth in the
    Eclipse Public License v. 2.0 are satisfied: GNU General Public License,
    version 2 with the GNU Classpath Exception, which is available at
    https://www.gnu.org/software/classpath/license.html.

    SPDX-License-Identifier: EPL-2.0 OR GPL-2.0 WITH Classpath-exception-2.0

-->
<!-- Portions Copyright [2019] [Payara Foundation and/or its affiliates] -->
<html lang="en">
  <head>
    <meta charset="utf-8"/>
    <title>create-cluster</title>
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <link href="css/style.css" rel="stylesheet">
    <script src="https://use.fontawesome.com/96c4d89611.js"></script>
  </head>
  <body>
<table id="doc-title" cellspacing="0" cellpadding="0">
  <tr>
  <td align="left" valign="top">
  <b>create-cluster</b><br />
  </td>
  </tr>
</table>
<hr />

<table width="90%" id="top-nav" cellspacing="0" cellpadding="0">
	<colgroup>
		<col width="12%"/>
		<col width="12%"/>
		<col width="*"/>
	</colgroup>
	<tr>
		<td align="left">
		<a href="create-auth-realm.html">
			<span class="vector-font"><i class="fa fa-arrow-circle-left" aria-hidden="true"></i></span>
			<span style="position:relative;top:-2px;">Previous</span>
		</a>
		</td>

		<td align="left">
		<a href="create-connector-connection-pool.html">
			<span class=" vector-font"><i class="fa fa-arrow-circle-right vector-font" aria-hidden="true"></i></span>
			<span style="position:relative;top:-2px;">Next</span>
		</a>
		</td>

		<td align="right">
		<a href="toc.html">
			<span class=" vector-font"><i class="fa fa-list vector-font" aria-hidden="true"></i></span>
			<span style="position:relative;top:-2px;">Contents</span>
		</a>
		</td>
	</tr>
</table>


<div id="preamble">
<div class="sectionbody">
<div class="paragraph">
<p><a id="create-cluster-1"></a><a id="GSRFM00017"></a><a id="create-cluster"></a></p>
</div>
</div>
</div>
<div class="sect1">
<h2 id="_create_cluster">create-cluster</h2>
<div class="sectionbody">
<div class="paragraph">
<p>creates a \{product---name} cluster</p>
</div>
<div id="sthref147" class="paragraph">
<p>Synopsis</p>
</div>
<div class="listingblock">
<div class="content">
<pre class="prettyprint highlight"><code class="language-oac_no_warn" data-lang="oac_no_warn">asadmin [asadmin-options] create-cluster [--help]
[--config config-name]
[--systemproperties (name=value)[:name=value]*]
[--properties (name=value)[:name=value]*]
[--gmsenabled={true|false}]
[--multicastport multicast-port]
[--multicastaddress multicast-address]
[--bindaddress bind-address]
[--hosts hadb-host-list]
[--haagentport port-number]
[--haadminpassword password]
[--haadminpasswordfile file-name] [--devicesize devicesize ]
[--haproperty (name=value)[:name=value]*]
[--autohadb=false] [--portbase port-number]
cluster-name</code></pre>
</div>
</div>
<div id="sthref148" class="paragraph">
<p>Description</p>
</div>
<div class="paragraph">
<p>The <code>create-cluster</code> subcommand creates a \{product---name} cluster.
Initially the cluster contains no \{product---name} instances,
applications, or resources.</p>
</div>
<div class="paragraph">
<p>A cluster requires a reference to the named configuration that defines
the configuration of all instances that are added to the cluster. The
configuration can be specified in the command to create the cluster, but
is not required. If no configuration is specified, the subcommand
creates a configuration that is named cluster-name`-config` for the
cluster. The cluster that is created is a standalone cluster because the
cluster&#8217;s configuration is not shared with any other clusters or
standalone instances.</p>
</div>
<div class="paragraph">
<p>To add instances to the cluster, set the <code>--cluster</code> option to the name
of the cluster when using either of the following subcommands:</p>
</div>
<div class="ulist">
<ul>
<li>
<p><a href="create-instance.html#create-instance-1"><code>create-instance</code>(1)</a></p>
</li>
<li>
<p><a href="create-local-instance.html#create-local-instance-1"><code>create-local-instance</code>(1)</a></p>
</li>
</ul>
</div>
<div class="paragraph">
<p>To delete server instances from the cluster at any time, use one of the
following subcommands:</p>
</div>
<div class="ulist">
<ul>
<li>
<p><a href="delete-instance.html#delete-instance-1"><code>delete-instance</code>(1)</a></p>
</li>
<li>
<p><a href="delete-local-instance.html#delete-local-instance-1"><code>delete-local-instance</code>(1)</a></p>
</li>
</ul>
</div>
<div class="paragraph">
<p>To associate applications and resources with all instances in the
cluster, set the <code>--target</code> option to the name of the cluster when
performing the following operations:</p>
</div>
<div class="ulist">
<ul>
<li>
<p>Deploying applications by using the
<a href="deploy.html#deploy-1"><code>deploy</code>(1)</a> subcommand</p>
</li>
<li>
<p>Creating resources by using subcommands such as
<a href="create-jdbc-resource.html#create-jdbc-resource-1"><code>create-jdbc-resource</code>(1)</a></p>
</li>
<li>
<p>Creating references to applications that are already deployed in other
targets by using the
<a href="create-application-ref.html#create-application-ref-1"><code>create-application-ref</code>(1)</a>
subcommand</p>
</li>
<li>
<p>Creating references to resources that are already created in other
targets by using the
<a href="create-resource-ref.html#create-resource-ref-1"><code>create-resource-ref</code>(1)</a>
subcommand</p>
</li>
</ul>
</div>
<div class="paragraph">
<p>This subcommand is supported in remote mode only.</p>
</div>
<div id="sthref149" class="paragraph">
<p>Options</p>
</div>
<div class="dlist">
<dl>
<dt class="hdlist1">asadmin-options</dt>
<dd>
<p>Options for the <code>asadmin</code> utility. For information about these
options, see the <a href="asadmin.html#asadmin-1m"><code>asadmin</code>(1M)</a> help page.</p>
</dd>
<dt class="hdlist1"><code>--help</code></dt>
<dt class="hdlist1"><code>-?</code></dt>
<dd>
<p>Displays the help text for the subcommand.</p>
</dd>
<dt class="hdlist1"><code>--config</code></dt>
<dd>
<p>Specifies the named configuration that the cluster references. The
configuration must exist and must not be named <code>default-config</code> or
<code>server-config</code>. Specifying the <code>--config</code> option creates a shared
cluster. If this option is omitted, a standalone cluster is created.</p>
</dd>
<dt class="hdlist1"><code>--systemproperties</code></dt>
<dd>
<p>Defines system properties for the configuration that is created for
the cluster. These properties override the property values in the
<code>default-config</code> configuration. The following properties are
available:<br></p>
<div class="dlist">
<dl>
<dt class="hdlist1"><code>ASADMIN_LISTENER_PORT</code></dt>
<dd>
<p>This property specifies the port number of the HTTP port or HTTPS
port through which the DAS connects to the instance to manage the
instance. Valid values are 1-65535. On UNIX, creating sockets that
listen on ports 1-1024 requires superuser privileges.</p>
</dd>
<dt class="hdlist1"><code>HTTP_LISTENER_PORT</code></dt>
<dd>
<p>This property specifies the port number of the port that is used to
listen for HTTP requests. Valid values are 1-65535. On UNIX,
creating sockets that listen on ports 1-1024 requires superuser
privileges.</p>
</dd>
<dt class="hdlist1"><code>HTTP_SSL_LISTENER_PORT</code></dt>
<dd>
<p>This property specifies the port number of the port that is used to
listen for HTTPS requests. Valid values are 1-65535. On UNIX,
creating sockets that listen on ports 1-1024 requires superuser
privileges.</p>
</dd>
<dt class="hdlist1"><code>IIOP_LISTENER_PORT</code></dt>
<dd>
<p>This property specifies the port number of the port that is used for
IIOP connections. Valid values are 1-65535. On UNIX, creating
sockets that listen on ports 1-1024 requires superuser privileges.</p>
</dd>
<dt class="hdlist1"><code>IIOP_SSL_LISTENER_PORT</code></dt>
<dd>
<p>This property specifies the port number of the port that is used for
secure IIOP connections. Valid values are 1-65535. On UNIX, creating
sockets that listen on ports 1-1024 requires superuser privileges.</p>
</dd>
<dt class="hdlist1"><code>IIOP_SSL_MUTUALAUTH_PORT</code></dt>
<dd>
<p>This property specifies the port number of the port that is used for
secure IIOP connections with client authentication. Valid values are
1-65535. On UNIX, creating sockets that listen on ports 1-1024
requires superuser privileges.</p>
</dd>
<dt class="hdlist1"><code>JAVA_DEBUGGER_PORT</code></dt>
<dd>
<p>This property specifies the port number of the port that is used for
connections to the Java Platform Debugger Architecture (JPDA)
debugger. Valid values are 1-65535. On UNIX, creating sockets that
listen on ports 1-1024 requires superuser privileges.</p>
</dd>
<dt class="hdlist1"><code>JMS_PROVIDER_PORT</code></dt>
<dd>
<p>This property specifies the port number for the Java Message Service
provider. Valid values are 1-65535. On UNIX, creating sockets that
listen on ports 1-1024 requires superuser privileges.</p>
</dd>
<dt class="hdlist1"><code>JMX_SYSTEM_CONNECTOR_PORT</code></dt>
<dd>
<p>This property specifies the port number on which the JMX connector
listens. Valid values are 1-65535. On UNIX, creating sockets that
listen on ports 1-1024 requires superuser privileges.</p>
</dd>
<dt class="hdlist1"><code>OSGI_SHELL_TELNET_PORT</code></dt>
<dd>
<p>This property specifies the port number of the port that is used for
connections to the
<a href="http://felix.apache.org/site/apache-felix-remote-shell.html">Apache
Felix Remote Shell</a>
(<a href="http://felix.apache.org/site/apache-felix-remote-shell.html" class="bare">http://felix.apache.org/site/apache-felix-remote-shell.html</a>). This
shell uses the Felix shell service to interact with the OSGi module
management subsystem. Valid values are 1-65535. On UNIX, creating
sockets that listen on ports 1-1024 requires superuser privileges.</p>
</dd>
</dl>
</div>
</dd>
<dt class="hdlist1"><code>--properties</code></dt>
<dd>
<p>Defines properties for the cluster. The following properties are
available:<br></p>
<div class="dlist">
<dl>
<dt class="hdlist1"><code>GMS_DISCOVERY_URI_LIST</code></dt>
<dd>
<p>The locations of \{product---name} instances in the cluster to use
for discovering the cluster. This property is required only if the
Group Management Service (GMS) is not using multicast for
broadcasting messages.<br>
Valid values for this property are as follows:<br></p>
<div class="ulist">
<ul>
<li>
<p>A comma-separated list of uniform resource identifiers (URIs).
Each URI must locate a \{product---name} instance or the DAS. This
format is required if multiple \{product---name} instances are
running on the same host.<br>
The format of each URI in the list is as follows:<br>
scheme`://<code>host-name-or -IP-address</code>:`port</p>
<div class="ulist">
<ul>
<li>
<p>scheme is the URI scheme, which is <code>tcp</code>.</p>
</li>
<li>
<p>host-name-or -IP-address is the host name or IP address of the
host on which the instance is running.</p>
</li>
<li>
<p>port is the port number of the port on which the instance listens
for messages from GMS. The system property
`GMS_LISTENER_PORT-`clustername must be set for the instance.</p>
</li>
</ul>
</div>
</li>
<li>
<p>A comma-separated list of IP addresses or host names on which the
DAS or the instances are running. The list can contain a mixture of
IP addresses and host names. This format can be used only if one
clustered instance is running on each host. The value of the
<code>GMS_LISTENER_PORT</code> property must be unique for each cluster in a
domain.</p>
</li>
<li>
<p>The keyword <code>generate</code>. This format can be used only if one
instance in a cluster is running on each host and the DAS is running
on a separate host. Multiple instances on the same host cannot be
members of the same cluster. The value of the <code>GMS_LISTENER_PORT</code>
property must be unique for each cluster in a domain.</p>
</li>
</ul>
</div>
</dd>
<dt class="hdlist1"><code>GMS_LISTENER_PORT</code></dt>
<dd>
<p>The port number of the port on which the cluster listens for
messages from GMS.<br>
The default value is a reference to the
<code>GMS_LISTENER_PORT-`cluster-name system property. By default, this
system property is not set. In this situation, GMS selects a free
port from the range that is defined by the properties
`GMS_TCPSTARTPORT</code> and <code>GMS_TCPENDPORT</code>. By default, this range is
9090-9200. In most situations, the default behavior should suffice.<br>
However, if GMS is not using multicast for broadcasting messages,
the <code>GMS_LISTENER_PORT</code> property must specify a port number that is
valid for all \{product---name} instances in the cluster. To use the
default value to meet this requirement, use a system property to set
the port number individually for each instance.<br>
For example, use the <code>create-system-properties</code> subcommand to create
the system property <code>GMS_LISTENER_PORT-`cluster-name for the DAS.
Then, for each instance in the cluster, set the
`GMS_LISTENER_PORT-`cluster-name system property to the port number
on which the instance listens for messages from GMS. The default
value of the `GMS_LISTENER_PORT</code> property for the cluster references
this system property.</p>
</dd>
<dt class="hdlist1"><code>GMS_LOOPBACK</code></dt>
<dd>
<p>Specifies whether an instance may receive from itself
application-level messages that the instance broadcasts to the
cluster.<br></p>
<div class="dlist">
<dl>
<dt class="hdlist1">Possible values are as follows</dt>
</dl>
</div>
</dd>
</dl>
</div>
</dd>
<dt class="hdlist1"><code>false</code></dt>
<dd>
<p>The instance may not receive messages from itself (default).</p>
</dd>
<dt class="hdlist1"><code>true</code></dt>
<dd>
<p>The instance may receive messages from itself. Use this setting
for testing an instance when the instance is the only instance in
a cluster.</p>
<div class="dlist">
<dl>
<dt class="hdlist1"><code>GMS_MULTICAST_TIME_TO_LIVE</code></dt>
<dd>
<p>The maximum number of iterations or transmissions that a multicast
message for the following types of events can experience before the
message is discarded:<br></p>
<div class="ulist">
<ul>
<li>
<p>Group discovery</p>
</li>
<li>
<p>Member heartbeats</p>
</li>
<li>
<p>Membership changes<br>
To match the configuration of the network on which the DAS and
clustered instances are deployed, set this value as low as possible.
To determine the lowest possible value for your system, use the
<a href="validate-multicast.html#validate-multicast-1"><code>validate-multicast</code>(1)</a>
subcommand.<br>
A value of 0 ensures that multicast messages never leave the host
from which they are broadcast.<br>
A value of 1 might prevent the broadcast of messages between hosts
on same subnet that are connected by a switch or a router.<br>
The default is 4, which ensures that messages are successfully
broadcast to all cluster members in networks where hosts are
connected by switches or routers.</p>
</li>
</ul>
</div>
</dd>
<dt class="hdlist1"><code>GMS_TCPENDPORT</code></dt>
<dd>
<p>The highest port number in the range from which GMS selects a free
port if the `GMS_LISTENER_PORT-`cluster-name system property is not
set. The default is 9200.</p>
</dd>
<dt class="hdlist1"><code>GMS_TCPSTARTPORT</code></dt>
<dd>
<p>The lowest port number in the range from which GMS selects a free
port if the `GMS_LISTENER_PORT-`cluster-name system property is not
set. The default is 9090.</p>
</dd>
</dl>
</div>
</dd>
<dt class="hdlist1"><code>--gmsenabled</code></dt>
<dd>
<p>Specifies whether GMS is enabled for the cluster.<br>
Possible values are as follows:<br></p>
<div class="dlist">
<dl>
<dt class="hdlist1"><code>true</code></dt>
<dd>
<p>GMS is enabled for the cluster (default).<br>
When GMS is enabled for a cluster, GMS is started in each server
instance in the cluster and in the DAS. The DAS participates in each
cluster for which this option is set to <code>true</code>.</p>
</dd>
<dt class="hdlist1"><code>false</code></dt>
<dd>
<p>GMS is disabled for the cluster.</p>
</dd>
</dl>
</div>
</dd>
<dt class="hdlist1"><code>--multicastaddress</code></dt>
<dd>
<p>The address on which GMS listens for group events. This option must
specify a multicast address in the range 224.0.0.0 through
239.255.255.255. The default is 228.9.XX.YY, where XX and YY are
automatically generated independent values between 0 and 255.</p>
</dd>
<dt class="hdlist1"><code>--multicastport</code></dt>
<dd>
<p>The port number of communication port on which GMS listens for group
events. This option must specify a valid port number in the range
2048-49151. The default is an automatically generated value in this
range.</p>
</dd>
<dt class="hdlist1"><code>--bindaddress</code></dt>
<dd>
<p>The Internet Protocol (IP) address of the network interface to which
GMS binds. This option must specify the IP address of a local network
interface. The default is all public network interface addresses.<br>
On a multihome machine, this option configures the network interface
that is used for the GMS. A multihome machine possesses two or more
network interfaces.<br>
To specify an address that is valid for all \{product---name}
instances in the cluster, use a system property to set the address
individually for each instance.<br>
For example, use the <code>create-system-properties</code> subcommand to create
the system property <code>GMS-BIND-INTERFACE-ADDRESS-`cluster-name. Then
set the `--bindaddress</code> option of this subcommand to
<code>${GMS-BIND-INTERFACE-ADDRESS-`cluster-name</code>}` to specify the system
property. Finally, for each instance in the cluster, set the
`GMS-BIND-INTERFACE-ADDRESS-`cluster-name system property to the
required network interface address on the instance&#8217;s machine.</p>
</dd>
<dt class="hdlist1"><code>--hosts</code></dt>
<dd>
<p>Do not specify this option. This option is retained for compatibility
with earlier releases. If you specify this option, a syntax error does
not occur. Instead, the subcommand runs successfully and displays a
warning message that the option is ignored.</p>
</dd>
<dt class="hdlist1"><code>--haagentport</code></dt>
<dd>
<p>Do not specify this option. This option is retained for compatibility
with earlier releases. If you specify this option, a syntax error does
not occur. Instead, the subcommand runs successfully and displays a
warning message that the option is ignored.</p>
</dd>
<dt class="hdlist1"><code>--haadminpassword</code></dt>
<dd>
<p>Do not specify this option. This option is retained for compatibility
with earlier releases. If you specify this option, a syntax error does
not occur. Instead, the subcommand runs successfully and displays a
warning message that the option is ignored.</p>
</dd>
<dt class="hdlist1"><code>--haadminpasswordfile</code></dt>
<dd>
<p>Do not specify this option. This option is retained for compatibility
with earlier releases. If you specify this option, a syntax error does
not occur. Instead, the subcommand runs successfully and displays a
warning message that the option is ignored.</p>
</dd>
<dt class="hdlist1"><code>--devicesize</code></dt>
<dd>
<p>Do not specify this option. This option is retained for compatibility
with earlier releases. If you specify this option, a syntax error does
not occur. Instead, the subcommand runs successfully and displays a
warning message that the option is ignored.</p>
</dd>
<dt class="hdlist1"><code>--haproperty</code></dt>
<dd>
<p>Do not specify this option. This option is retained for compatibility
with earlier releases. If you specify this option, a syntax error does
not occur. Instead, the subcommand runs successfully and displays a
warning message that the option is ignored.</p>
</dd>
<dt class="hdlist1"><code>--autohadb</code></dt>
<dd>
<p>Do not specify this option. This option is retained for compatibility
with earlier releases. If you specify this option, a syntax error does
not occur. Instead, the subcommand runs successfully and displays a
warning message that the option is ignored.</p>
</dd>
<dt class="hdlist1"><code>--portbase</code></dt>
<dd>
<p>Do not specify this option. This option is retained for compatibility
with earlier releases. If you specify this option, a syntax error does
not occur. Instead, the subcommand runs successfully and displays a
warning message that the option is ignored.</p>
</dd>
</dl>
</div>
<div id="sthref150" class="paragraph">
<p>Operands</p>
</div>
<div class="dlist">
<dl>
<dt class="hdlist1">cluster-name</dt>
<dd>
<p>The name of the cluster.<br>
The name must meet the following requirements:<br></p>
<div class="ulist">
<ul>
<li>
<p>The name may contain only ASCII characters.</p>
</li>
<li>
<p>The name must start with a letter, a number, or an underscore.</p>
</li>
<li>
<p>The name may contain only the following characters:</p>
<div class="ulist">
<ul>
<li>
<p>Lowercase letters</p>
</li>
<li>
<p>Uppercase letters</p>
</li>
<li>
<p>Numbers</p>
</li>
<li>
<p>Hyphen</p>
</li>
<li>
<p>Period</p>
</li>
<li>
<p>Underscore</p>
</li>
</ul>
</div>
</li>
<li>
<p>The name must be unique in the domain and must not be the name of
another cluster, a named configuration, a \{product---name} instance,
or a node.</p>
</li>
<li>
<p>The name must not be <code>domain</code>, <code>server</code>, or any other keyword that
is reserved by \{product---name}.<br>
If the
<a href="configure-jms-cluster.html#configure-jms-cluster-1"><code>configure-jms-cluster</code>(1)</a>
subcommand is to be used to configure a Message Queue cluster to
provide JMS services to the \{product---name} cluster, the length of
the \{product---name} cluster name is might be restricted:<br></p>
</li>
<li>
<p>If <code>clustertype</code> is set to <code>enhanced</code> in the
<a href="configure-jms-cluster.html#configure-jms-cluster-1"><code>configure-jms-cluster</code>(1)</a>
subcommand, the name can be no longer than n–21 characters, where n is
the maximum table name length allowed by the database.</p>
</li>
<li>
<p>If <code>configstoretype</code> is set to <code>shareddb</code> in the
<a href="configure-jms-cluster.html#configure-jms-cluster-1"><code>configure-jms-cluster</code>(1)</a>
subcommand, the name can be no longer than n–19 characters, where n is
the maximum table name length allowed by the database.</p>
</li>
</ul>
</div>
</dd>
</dl>
</div>
<div id="sthref151" class="paragraph">
<p>Examples</p>
</div>
<div class="paragraph">
<p><a id="GSRFM462"></a><a id="sthref152"></a></p>
</div>
<div class="paragraph">
<p>Example 1   Creating a Cluster</p>
</div>
<div class="paragraph">
<p>This example creates a cluster that is named <code>ltscluster</code> for which port
1169 is to be used for secure IIOP connections. Because the <code>--config</code>
option is not specified, the cluster references a copy of the named
configuration <code>default-config</code> that is named <code>ltscluster-config</code>.</p>
</div>
<div class="listingblock">
<div class="content">
<pre class="prettyprint highlight"><code class="language-oac_no_warn" data-lang="oac_no_warn">asadmin&gt; create-cluster
--systemproperties IIOP_SSL_LISTENER_PORT=1169
ltscluster
Command create-cluster executed successfully.</code></pre>
</div>
</div>
<div class="paragraph">
<p><a id="GSRFM463"></a><a id="sthref153"></a></p>
</div>
<div class="paragraph">
<p>Example 2   Creating a Cluster With a List of URIs for Discovering the
Cluster</p>
</div>
<div class="paragraph">
<p>This example creates a cluster that is named <code>tcpcluster</code>. In this
example, GMS is not using multicast for broadcasting messages and
multiple instances reside on the same host. Therefore, the
<code>GMS_DISCOVERY_URI_LIST</code> property is set to the locations of the
\{product---name} instances to use for discovering the cluster. These
instances reside on the host whose IP address is <code>10.152.23.224</code> and
listen for GMS events on ports 9090, 9091, and 9092.</p>
</div>
<div class="paragraph">
<p>To distinguish colon (<code>:</code>) characters in URIs from separators in a
property list, colons in URIs are escaped with single quote characters
(<code>'</code>) and backslash (<code>\</code>) characters. For more information about escape
characters in options for the <code>asadmin</code> utility, see the
<a href="asadmin.html#asadmin-1m"><code>asadmin</code>(1M)</a> help page.</p>
</div>
<div class="paragraph">
<p>This example assumes that the port on which each instance listens for
GMS messages is set independently for the instance through the
<code>GMS_LISTENER_PORT-tcpcluster</code> system property.</p>
</div>
<div class="listingblock">
<div class="content">
<pre class="prettyprint highlight"><code class="language-oac_no_warn" data-lang="oac_no_warn">asadmin&gt; create-cluster --properties GMS_DISCOVERY_URI_LIST=
tcp'\\:'//10.152.23.224'\\:'9090,
tcp'\\:'//10.152.23.224'\\:'9091,
tcp'\\:'//10.152.23.224'\\:'9092 tcpcluster
Command create-cluster executed successfully.</code></pre>
</div>
</div>
<div class="paragraph">
<p><a id="GSRFM827"></a><a id="sthref154"></a></p>
</div>
<div class="paragraph">
<p>Example 3   Creating a Cluster With a List of IP Addresses for
Discovering the Cluster</p>
</div>
<div class="paragraph">
<p>This example creates a cluster that is named <code>ipcluster</code>. In this
example, GMS is not using multicast for broadcasting messages and only
one clustered instance resides on each host. Therefore, the
<code>GMS_DISCOVERY_URI_LIST</code> property is set to the IP addresses of the
hosts where instances to use for discovering the cluster are running.
The cluster listens for messages from GMS on port 9090.</p>
</div>
<div class="listingblock">
<div class="content">
<pre class="prettyprint highlight"><code class="language-oac_no_warn" data-lang="oac_no_warn">asadmin&gt; create-cluster --properties 'GMS_DISCOVERY_URI_LIST=
10.152.23.225,10.152.23.226,10.152.23.227,10.152.23.228:
GMS_LISTENER_PORT=9090' ipcluster
Command create-cluster executed successfully.</code></pre>
</div>
</div>
<div class="paragraph">
<p><a id="GSRFM828"></a><a id="sthref155"></a></p>
</div>
<div class="paragraph">
<p>Example 4   Creating a Cluster With a Generated List of Instances for
Discovering the Cluster</p>
</div>
<div class="paragraph">
<p>This example creates a cluster that is named <code>gencluster</code>. In this
example, GMS is not using multicast for broadcasting messages, one
instance in the cluster is running on each host and the DAS is running
on a separate host. Therefore, the <code>GMS_DISCOVERY_URI_LIST</code> property is
set to the keyword <code>generate</code> to generate a list of instances to use for
discovering the cluster. The cluster listens for messages from GMS on
port 9090.</p>
</div>
<div class="listingblock">
<div class="content">
<pre class="prettyprint highlight"><code class="language-oac_no_warn" data-lang="oac_no_warn">asadmin&gt; create-cluster --properties 'GMS_DISCOVERY_URI_LIST=generate:
GMS_LISTENER_PORT=9090' gencluster
Command create-cluster executed successfully.</code></pre>
</div>
</div>
<div id="sthref156" class="paragraph">
<p>Exit Status</p>
</div>
<div class="dlist">
<dl>
<dt class="hdlist1">0</dt>
<dd>
<p>command executed successfully</p>
</dd>
<dt class="hdlist1">1</dt>
<dd>
<p>error in executing the command</p>
</dd>
</dl>
</div>
<div id="sthref157" class="paragraph">
<p>See Also</p>
</div>
<div class="paragraph">
<p><a href="asadmin.html#asadmin-1m"><code>asadmin</code>(1M)</a></p>
</div>
<div class="paragraph">
<p><a href="create-application-ref.html#create-application-ref-1"><code>create-application-ref</code>(1)</a>,
<a href="create-instance.html#create-instance-1"><code>create-instance</code>(1)</a>,
<a href="create-jdbc-resource.html#create-jdbc-resource-1"><code>create-jdbc-resource</code>(1)</a>,
<a href="create-local-instance.html#create-local-instance-1"><code>create-local-instance</code>(1)</a>,
<a href="create-resource-ref.html#create-resource-ref-1"><code>create-resource-ref</code>(1)</a>,
<a href="delete-cluster.html#delete-cluster-1"><code>delete-cluster</code>(1)</a>,
<a href="delete-instance.html#delete-instance-1"><code>delete-instance</code>(1)</a>,
<a href="delete-local-instance.html#delete-local-instance-1"><code>delete-local-instance</code>(1)</a>,
<a href="deploy.html#deploy-1"><code>deploy</code>(1)</a>,
<a href="list-clusters.html#list-clusters-1"><code>list-clusters</code>(1)</a>,
<a href="start-cluster.html#start-cluster-1"><code>start-cluster</code>(1)</a>,
<a href="stop-cluster.html#stop-cluster-1"><code>stop-cluster</code>(1)</a>,
<a href="validate-multicast.html#validate-multicast-1"><code>validate-multicast</code>(1)</a></p>
</div>
<div class="paragraph">
<p>Apache Felix Remote Shell
(<a href="http://felix.apache.org/site/apache-felix-remote-shell.html" class="bare">http://felix.apache.org/site/apache-felix-remote-shell.html</a>)
</div>
</div>
</div>

<hr />

<table width="90%" id="bottom-nav" cellspacing="0" cellpadding="0">
	<colgroup>
		<col width="12%"/>
		<col width="12%"/>
		<col width="*"/>
	</colgroup>
	<tr>		
		<td align="left">
		<a href="create-auth-realm.html">
			<span class=" vector-font"><i class="fa fa-arrow-circle-left" aria-hidden="true"></i></span>
			<span style="position:relative;top:-2px;">Previous</span>
		</a>
		</td>

		<td align="left">
		<a href="create-connector-connection-pool.html">
			<span class="vector-font"><i class="fa fa-arrow-circle-right vector-font" aria-hidden="true"></i></span>
			<span style="position:relative;top:-2px;">Next</span>
		</a>
		</td>

		<td align="right">
		<a href="toc.html">
			<span class="vector-font"><i class="fa fa-list vector-font" aria-hidden="true"></i></span>
			<span style="position:relative;top:-2px;">Contents</span>
		</a>
		</td>
	</tr>
</table>

<span id="copyright">
        <img src="/resource/reference/img/eclipse_foundation_logo_tiny.png" height="20px" alt="Eclipse Foundation Logo" align="top"/>&nbsp;            
        <span >Copyright&nbsp;&copy;&nbsp;2019,&nbsp;Oracle&nbsp;and/or&nbsp;its&nbsp;affiliates.&nbsp;All&nbsp;rights&nbsp;reserved.</span>
</span>

</body>
</html>
